Skip to content

Add tooltips to icon-only buttons - #264

Open
alex-rawlings-yyc wants to merge 5 commits into
mainfrom
219-tooltips-icon-only-buttons
Open

Add tooltips to icon-only buttons#264
alex-rawlings-yyc wants to merge 5 commits into
mainfrom
219-tooltips-icon-only-buttons

Conversation

@alex-rawlings-yyc

@alex-rawlings-yyc alex-rawlings-yyc commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Every control that showed only an icon had its wording reachable by screen readers alone; each now names its action on hover. The mock Tooltip gained the provider requirement the real one enforces, which caught the view-options dropdown rendering outside every provider.


This change is Reviewable

Summary by CodeRabbit

  • New Features

    • Added localized hover tooltips for phrase editing, token removal, linking, arc splitting, view options, and active-verse controls.
    • Added clearer accessible labels for adding tokens to phrases.
    • Tooltips now appear only when relevant and are hidden when actions are unavailable or panels are open.
  • UI Improvements

    • Improved hover visibility and styling across light and dark themes.
    • Updated phrase layouts with better spacing around floating controls.
    • Improved focus and navigation consistency across continuous and segment views.
  • Bug Fixes

    • Disabled controls can now provide helpful hover guidance without affecting keyboard accessibility.

@alex-rawlings-yyc alex-rawlings-yyc self-assigned this Aug 21, 2026
@coderabbitai

coderabbitai Bot commented Aug 21, 2026

Copy link
Copy Markdown

Review Change Stack

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 896874ba-26e9-4f93-a7ae-f642f1c9d691

📝 Walkthrough

Walkthrough

The change adds localized tooltips, enforces TooltipProvider usage, centralizes focus handling in FocusStore, propagates an add-token label through phrase-strip context, updates tests, and increases non-arc phrase top padding for the controls pill.

Changes

Tooltip, focus, and phrase-strip enhancements

Layer / File(s) Summary
Tooltip provider infrastructure
__mocks__/platform-bible-react.tsx, src/components/tooltip-delay.ts, src/__tests__/components/test-helpers.tsx, src/__tests__/components/*
Tooltip triggers forward props and require TooltipProvider. Shared delay and test helpers support provider-wrapped rendering.
Localized tooltip controls
src/components/ArcOverlay.tsx, src/components/PhraseBox.tsx, src/components/TokenChip.tsx, src/components/TokenLinkIcon.tsx, src/components/SegmentListView.tsx, src/components/controls/ViewOptionsDropdown.tsx, src/__tests__/components/*
Controls render localized tooltip content when labels resolve. Tests cover unresolved labels, disabled states, accessible labels, and existing interactions.
Focus store coordination
src/components/Interlinearizer.tsx, src/components/ContinuousView.tsx, src/components/SegmentListView.tsx, src/__tests__/components/Interlinearizer.test.tsx
Focus state, navigation, selection, scrolling, and transition handling use FocusStore through FocusProvider instead of parent-controlled props and callbacks.
Phrase context and control spacing
contributions/localizedStrings.json, src/components/SegmentView.tsx, src/components/PhraseStripContext.tsx, src/hooks/usePhraseStripSetup.ts, src/components/ContinuousView.tsx, src/utils/phrase-arc.ts, src/__tests__/utils/phrase-arc.test.ts
The add-token localization template flows into phrase-strip context. Non-arc phrases reserve 28 px for the full controls pill, with coverage for arc and fallback cases.

Estimated code review effort: 3 (Moderate) | ~30 minutes

Merge Risk: 🟡 Moderate · up to 5811c

At the current head, a same-group focus change can leave the continuous strip invisible, while some tooltips may still show an unresolved localization key and arc rendering may reserve excess space. These are bounded user-visible correctness issues, so the PR is not merge-ready until they are fixed or explicitly accepted.

Sequence Diagram(s)

sequenceDiagram
  participant Interlinearizer
  participant FocusProvider
  participant ContinuousView
  participant SegmentListView
  Interlinearizer->>FocusProvider: provide shared focus state
  FocusProvider->>ContinuousView: provide focus and navigation actions
  FocusProvider->>SegmentListView: provide focus and selection actions
  ContinuousView->>FocusProvider: update focused token
  SegmentListView->>FocusProvider: select focused segment
Loading

Suggested reviewers: imnasnainaec

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the primary change: adding tooltips to icon-only controls.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 29 functions across 24 files.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 219-tooltips-icon-only-buttons

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@alex-rawlings-yyc alex-rawlings-yyc linked an issue Aug 21, 2026 that may be closed by this pull request
coderabbitai[bot]

This comment was marked as outdated.

@alex-rawlings-yyc alex-rawlings-yyc left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alex-rawlings-yyc resolved 1 discussion.
Reviewable status: 0 of 25 files reviewed, all discussions resolved.

@imnasnainaec imnasnainaec left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imnasnainaec reviewed 12 files and all commit messages, and made 5 comments.
Reviewable status: 12 of 25 files reviewed, 5 unresolved discussions (waiting on alex-rawlings-yyc).


src/components/ArcOverlay.tsx line 317 at r2 (raw file):

                    // `dark:hover:bg-background` is needed alongside the light one: the ghost variant
                    // dims to `dark:hover:bg-muted/50`, and Tailwind's merge treats `hover:bg-*` and
                    // `dark:hover:bg-*` as separate groups, so overriding one leaves the other standing.

⛏️ I'm not sure but this might be overexplaining tw functionality.


src/components/TokenChip.tsx line 391 at r2 (raw file):

              // alongside the light one: the ghost variant dims to `dark:hover:bg-muted/50`, and
              // Tailwind's merge treats `hover:bg-*` and `dark:hover:bg-*` as separate groups, so
              // overriding one leaves the other standing.

⛏️ I'm not sure but this might be overexplaining tw functionality.


src/components/TokenLinkIcon.tsx line 289 at r2 (raw file):

  // the slot straddles a segment boundary explains that instead — the reason outranks the action,
  // since naming an action the click won't perform is worse than naming none. The other disabled
  // reasons (unlink/edit mode) stay silent, their cause already visible in the UI.

⛏️ much of this comment appears to be pr-diff-justifying and lacking persistent value.


src/components/TokenLinkIcon.tsx line 356 at r2 (raw file):

  return (
    <Tooltip>
      {/* A disabled button is not a hover target, so the trigger rides a wrapper span that is. */}

⛏️ putting a span between a tooltip and a disablable child is standard procedure and doesn't require a comment.


src/components/tooltip-delay.ts line 4 at r2 (raw file):

 * Hover delay, in milliseconds, before any tooltip in the extension opens. The interlinear view and
 * the tab toolbar sit in separate React trees and so need a `TooltipProvider` each; both read this
 * value, so a tooltip does not open on a different clock depending on which tree it belongs to.

⛏️ "does not open on a different clock..." could be reworded away from the double-negative to a positive about what it does.

Every control that showed only an icon had its wording reachable by
screen readers alone; each now names its action on hover. The mock
`Tooltip` gained the provider requirement the real one enforces, which
caught the view-options dropdown rendering outside every provider.
Its sibling branch already ran its label through `resolvedOrEmpty`, so a
cross-segment slot could show a raw `%…%` key as hover text while PAPI's
localization was still in flight.
@alex-rawlings-yyc
alex-rawlings-yyc force-pushed the 219-tooltips-icon-only-buttons branch from c66c342 to 62c8bac Compare August 25, 2026 18:21

@alex-rawlings-yyc alex-rawlings-yyc left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alex-rawlings-yyc made 5 comments.
Reviewable status: 12 of 25 files reviewed, 5 unresolved discussions (waiting on imnasnainaec).


src/components/ArcOverlay.tsx line 317 at r2 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

⛏️ I'm not sure but this might be overexplaining tw functionality.

Agreed — how tw-merge groups variants is Tailwind's to teach, not this file's. Cut to the constraint that actually has to hold, which is what a reader needs to know before touching the classes.


src/components/TokenChip.tsx line 391 at r2 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

⛏️ I'm not sure but this might be overexplaining tw functionality.

Same trim as the ArcOverlay one.


src/components/TokenLinkIcon.tsx line 289 at r2 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

⛏️ much of this comment appears to be pr-diff-justifying and lacking persistent value.

Agreed — the "the reason outranks the action" half was arguing for the choice rather than describing the code, which our comment rules call out directly ("the audience is the next reader of the code — never the reviewer of the current diff"). Kept the part that answers a real question for the next reader, namely which disabled states are deliberately silent.


src/components/TokenLinkIcon.tsx line 356 at r2 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

⛏️ putting a span between a tooltip and a disablable child is standard procedure and doesn't require a comment.

Agreed, dropped. It appeared twice in this file — the unlink trigger above had the same comment — so both are gone.


src/components/tooltip-delay.ts line 4 at r2 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

⛏️ "does not open on a different clock..." could be reworded away from the double-negative to a positive about what it does.

Reworded to the positive. Naming the two trees was also documenting consumers, which goes stale silently as trees are added or moved, so that went too.

@imnasnainaec imnasnainaec left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imnasnainaec reviewed all commit messages, made 1 comment, and resolved 5 discussions.
Reviewable status: 8 of 25 files reviewed, 1 unresolved discussion (waiting on alex-rawlings-yyc).


src/utils/phrase-arc.ts line 10 at r3 (raw file):

 * it, so only this half rises into the gap above.
 */
const CONTROLS_HALF_HEIGHT_PX = 12;

⛏️ Unless this "HALF" is half of something that still exist, Devin suggests something functionally descriptive like CONTROLS_ARC_OVERHANG_PX or CONTROLS_ARC_RISE_PX.

12 stopped being half of anything once the pill was measured directly
and
CONTROLS_HEIGHT_PX = 28 became its own constant. Name the overhang for
what
it is and drop the stale framing from the two docs that echoed it.

@alex-rawlings-yyc alex-rawlings-yyc left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alex-rawlings-yyc made 1 comment.
Reviewable status: 8 of 25 files reviewed, 1 unresolved discussion (waiting on imnasnainaec).


src/utils/phrase-arc.ts line 10 at r3 (raw file):

Previously, imnasnainaec (D. Ror.) wrote…

⛏️ Unless this "HALF" is half of something that still exist, Devin suggests something functionally descriptive like CONTROLS_ARC_OVERHANG_PX or CONTROLS_ARC_RISE_PX.

Done — renamed to CONTROLS_ARC_OVERHANG_PX, and swept the same stale "half" framing out of the computeStripTopPadding and computeStripRowGap docs.

It wasn't just vague — 12 hasn't been half of anything since CONTROLS_HEIGHT_PX = 28 landed as its own constant (28/2 is 14).

Left the value at 12; changing it to CONTROLS_HEIGHT_PX / 2 is a row-spacing change, not a naming fix.

coderabbitai[bot]

This comment was marked as outdated.

An external focus move fades the strip out and defers the
displayed-focus
update until the fade completes. The reveal was then left to the scroll
effect, which is keyed to focusPhraseIndex — so a move landing in the
group
already displayed never triggered it, and the strip stayed at opacity 0
indefinitely.

Reveal from the focus effect instead, whenever the displayed focus has
caught
up with the live one. Gating that on having canceled a live fade does
not
work: a fade that reaches its timeout clears its own handle before
committing
the displayed ref, so there is nothing left to cancel by the time the
effect
re-runs.

cancelPendingFade no longer reports whether it canceled anything, since
no
caller reads it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add tooltips to icon-only buttons

2 participants